Add defend.network to Security - #50
Open
zinvite wants to merge 1 commit into
Open
Conversation
Free, no-auth CC BY 4.0 JSON API of recently exploited CVEs enriched with CVSS, EPSS, and CISA KEV status. Docs: https://defend.network/api/ https://github.com/tools-collection/apis-collection
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds defend.network under the Security category.
A free, no-auth JSON API of recently exploited CVEs, each enriched with CVSS, EPSS, and CISA KEV status (with due dates) and an exploitation-state field. Updated daily (~04:00 UTC), published under CC BY 4.0, with CORS enabled and curl/Python examples in the docs.
Per CONTRIBUTING, I added
collection/defend-network.yamland rannpm run build; the generatedREADME.mdentry andpages/defend-network/README.mdare included. The README is not edited by hand.Checklist
npm run validatereports no errors fordefend-network.yaml)defend-network)categories.yaml(Security)npm run buildran successfullyNote: CI on
mainis currently red independently of this change —npm run validateexits non-zero due to ~564 pre-existinglogo: nullschema errors in other collection files, and the test suites fail to import because they reference../src/*.jswhile the sources now live incli/. This PR adds a single new, schema-valid entry and does not touch those files.